Cucumber Features

Expand All

Collapse All

@regression @module1 @sd @brm @fst

Feature: Service Desk BRM - Financial Systems Team - Request

Background

  1. Given I login as a RackerBrm2
    features/step_definitions/global_steps.rb:1
@flex_field_requestfeatures/service_desk_module/service_desk_brm_module/fst_request/change_flexfield_request.feature:7

Scenario Outline: : Creation of New Flexfield Request by Racker and validation of Task by SD Tech

  1. When I create a Change Flexfield Request - <request_type> BRM-request
    features/service_desk_module/service_desk_brm_module/fst_request/change_flexfield_request.feature:8
  2. And once the SEC Approver and SEC Director Approves the request
    features/service_desk_module/service_desk_brm_module/fst_request/change_flexfield_request.feature:9
  3. And as a Technician I validate EBS, BRM, HFM Tasks and close each request
    features/service_desk_module/service_desk_brm_module/fst_request/change_flexfield_request.feature:10
  4. Then As a Racker I validate that the FST request is closed
    features/service_desk_module/service_desk_brm_module/fst_request/change_flexfield_request.feature:11

Examples

request_type
Rename
Request Number : RITM0106243, EBS FlexField Task # : TASK0115695 , BRM FlexField Task # : TASK0115696 , HFM FlexField Task # : TASK0115697
@regression @module1 @sd @brm @new_fst

Feature: Service Desk BRM - FST Request - Account

Background

  1. Given I login as a RackerFST4
    features/step_definitions/global_steps.rb:1
@fst_accountfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:7

Scenario: New FST Flexfield - Account Request - E2E Flow

  1. When I create a New Flexfield Request - Account BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Account - FIN0001479
  3. Pizza Tracker values for Account displayed ["Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Account Creation", "HFM Account Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending Fin. Reporting Approval as expected
  5. And once the FRT, FRD Approves the BRM FST request
    features/step_definitions/sd_request_steps.rb:113
  6. Alert Message for Account dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Account #" on Request ( Edit Account button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  7. FST_FRT_Approver - Approved the Request
  8. FRD - Approved the Request
  9. And as a Technician I validate EBS, HFM FST-Tasks and close each request
    features/step_definitions/sd_request_steps.rb:91
  10. EBS FlexField Task # : TASK0115698
  11. HFM FlexField Task # : TASK0115699
  12. Then As a RackerFST4 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  13. Current Pizza Tracker stage displayed Done as expected
@fst_account_rejectfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:14

Scenario: New FST Flexfield - Account Request - SEC Director Reject and Racker Resubmission - E2E Flow

  1. When I create a New Flexfield Request - Account BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Account - FIN0001480
  3. Pizza Tracker values for Account displayed ["Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Account Creation", "HFM Account Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending Fin. Reporting Approval as expected
  5. And As a Financial Reporting Director I Reject the request
    features/step_definitions/sd_request_steps.rb:562
  6. Alert Message for Account dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Account #" on Request ( Edit Account button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  7. FST_FRT_Approver - Approved the Request
  8. FRD - Rejecting the Request
  9. And RackerFST4 Resubmits the FST Account request
    features/step_definitions/sd_request_steps.rb:576
  10. Pizza Tracker does not highlight any stage for Rejected request
  11. Stage displayed 'Rejected' as expected
  12. Pizza Tracker values for Account displayed ["Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Account Creation", "HFM Account Creation", "Done"] as expected
  13. And Once All the FST Approvals and Tasks are closed
    features/step_definitions/sd_request_steps.rb:591
    expected true
     got nil
 (RSpec::Expectations::ExpectationNotMetError)
    ./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
    1164    @page.request_number_search.value = "*#{@ritm_number}"
1165    @page.request_number_search.send_keys :enter
1166    expect(@page.myapprovals_table_firstcell.visible?).to be true
1167    fail 'Table has not had any data. ' if @page.my_approver_table.rows.empty?
1168    @page.myapprovals_table_firstcell.click
  14. Then As a RackerFST4 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
    15. Screenshot
     
@fst_account_validationfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_account_request.feature:22

Scenario: New FST Flexfield - Account Request - Catalog Page Validation

  1. And I am on BRM-Portal > Catalog Item - New Flexfield Request - Account Page
    features/step_definitions/sd_request_steps.rb:477
  2. Then I validate New Flexfield Request - Account Catalog Page
    features/step_definitions/sd_request_steps.rb:612
  3. Alert Message for Account Type 'Expense' dispayed 'Please select an Income / Expense Category prior to submission.' as mandatory as expected
  4. The Check Boxes 'COR, R&D, S&M, G&A, D&A, OTHER, INC_TAX' are displayed for 'Expense' as expected
  5. The Check Boxes 'COR, R&D, S&M, G&A, D&A, OTHER, INC_TAX' are not displayed for ["Asset", "Equity", "Liability", "Revenue"] as expected
@regression @module1 @sd @brm @new_fst

Feature: Service Desk BRM - FST Request - Company

Background

  1. Given I login as a RackerFST2
    features/step_definitions/global_steps.rb:1
@fst_companyfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_company_request.feature:7

Scenario: New FST Flexfield - Company Request - E2E Flow

  1. When I create a New Flexfield Request - Company BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Company - FIN0001482
  3. Pizza Tracker values for Company displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Company Creation", "HFM Company Creation", "HR Company Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending FPNA Approval as expected
  5. And once the FPNA, FRT, FRD Approves the BRM FST request
    features/step_definitions/sd_request_steps.rb:113
  6. FPNA - Approved the Request
  7. Alert Message for Company dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Company #", "Appropriate Ledger" and "Company's Functional Currency", on Request ( Edit Company button) that will be used in Oracle and downstream systems. This needs to be inputted prior to approval.'
  8. FST_FRT_Approver - Approved the Request
  9. FRD - Approved the Request
  10. And as a Technician I validate EBS, HFM, HR FST-Tasks and close each request
    features/step_definitions/sd_request_steps.rb:91
  11. EBS FlexField Task # : TASK0115700
  12. HFM FlexField Task # : TASK0115701
  13. HR FlexField Task # : HR0069002
  14. Then As a RackerFST2 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  15. Current Pizza Tracker stage displayed Done as expected
@fst_company_rejectfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_company_request.feature:14

Scenario: New FST Flexfield - Company Request - SEC Director Reject and Racker Resubmission - E2E Flow

  1. When I create a New Flexfield Request - Company BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Company - FIN0001483
  3. Pizza Tracker values for Company displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Company Creation", "HFM Company Creation", "HR Company Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending FPNA Approval as expected
  5. And As a Financial Reporting Director I Reject the request
    features/step_definitions/sd_request_steps.rb:562
  6. FPNA - Approved the Request
  7. Alert Message for Company dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Company #", "Appropriate Ledger" and "Company's Functional Currency", on Request ( Edit Company button) that will be used in Oracle and downstream systems. This needs to be inputted prior to approval.'
  8. FST_FRT_Approver - Approved the Request
  9. FRD - Rejecting the Request
  10. And RackerFST2 Resubmits the FST Company request
    features/step_definitions/sd_request_steps.rb:576
  11. Pizza Tracker does not highlight any stage for Rejected request
  12. Stage displayed 'Rejected' as expected
  13. Pizza Tracker values for Company displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Company Creation", "HFM Company Creation", "HR Company Creation", "Done"] as expected
  14. And Once All the FST Approvals and Tasks are closed
    features/step_definitions/sd_request_steps.rb:591
  15. FPNA - Approved the Request
  16. Alert Message for Company dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Company #", "Appropriate Ledger" and "Company's Functional Currency", on Request ( Edit Company button) that will be used in Oracle and downstream systems. This needs to be inputted prior to approval.'
  17. FST_FRT_Approver - Approved the Request
  18. FRD - Approved the Request
  19. EBS FlexField Task # : TASK0115702
  20. HFM FlexField Task # : TASK0115703
  21. HR FlexField Task # : HR0069003
  22. Then As a RackerFST2 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  23. Current Pizza Tracker stage displayed Done as expected
@regression @module1 @sd @brm @new_fst

Feature: Service Desk BRM - FST Request - Cross Validation

Background

  1. Given I login as a RackerBrm2
    features/step_definitions/global_steps.rb:1
@fst_cross_validationfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_cross_validation_request.feature:7

Scenario: New FST - Submit a Cross Validation Request - E2E Flow

  1. When I create a FST Submit a Cross Validation Request
    features/step_definitions/sd_request_steps.rb:621
  2. FST # for Submit a Cross Validation - FIN0001484
  3. Pizza Tracker values for Submit a Cross Validation displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Cross Validation Creation", "HFM Cross Validation Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending FPNA Approval as expected
  5. And once the FPNA, FRT, FRD Approves the BRM FST request
    features/step_definitions/sd_request_steps.rb:113
  6. FPNA - Approved the Request
  7. FRT - Approved the Request
  8. FRD - Approved the Request
  9. And as a Technician I validate EBS, HFM FST-Tasks and close each request
    features/step_definitions/sd_request_steps.rb:91
  10. EBS FlexField Task # : TASK0115704
  11. HFM FlexField Task # : TASK0115705
  12. Then As a RackerBrm2 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  13. Current Pizza Tracker stage displayed Done as expected
@regression @module1 @sd @brm @new_fst

Feature: Service Desk BRM - FST Request - Department

Background

  1. Given I login as a RackerFST7
    features/step_definitions/global_steps.rb:1
@fst_departmentfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_department_request.feature:7

Scenario: New FST Flexfield - Department Request - E2E Flow

  1. When I create a New Flexfield Request - Department BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Department - FIN0001485
  3. Pizza Tracker values for Department displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Department Creation", "HFM Department Creation", "HR Department Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending FPNA Approval as expected
  5. And once the FPNA, FRT, FRD Approves the BRM FST request
    features/step_definitions/sd_request_steps.rb:113
  6. FPNA - Approved the Request
  7. Alert Message for Department dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Department #" on Request ( Edit Department button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  8. FST_FRT_Approver - Approved the Request
  9. FRD - Approved the Request
  10. And as a Technician I validate EBS, HFM, HR FST-Tasks and close each request
    features/step_definitions/sd_request_steps.rb:91
  11. EBS FlexField Task # : TASK0115706
  12. HFM FlexField Task # : TASK0115707
  13. HR FlexField Task # : HR0069004
  14. Then As a RackerFST7 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  15. Current Pizza Tracker stage displayed Done as expected
@fst_department_rejectfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_department_request.feature:14

Scenario: New FST Flexfield - Department Request - SEC Director Reject and Racker Resubmission - E2E Flow

  1. When I create a New Flexfield Request - Department BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Department - FIN0001486
  3. Pizza Tracker values for Department displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Department Creation", "HFM Department Creation", "HR Department Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending FPNA Approval as expected
  5. And As a Financial Reporting Director I Reject the request
    features/step_definitions/sd_request_steps.rb:562
  6. FPNA - Approved the Request
  7. Alert Message for Department dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Department #" on Request ( Edit Department button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  8. FST_FRT_Approver - Approved the Request
  9. FRD - Rejecting the Request
  10. And RackerFST7 Resubmits the FST Department request
    features/step_definitions/sd_request_steps.rb:576
  11. Pizza Tracker does not highlight any stage for Rejected request
  12. Stage displayed 'Rejected' as expected
    13. expected: ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Department Creation", "HFM Department Creation", "HR Department Creation", "Done"]
     got: ["Pending Finance Partner Approval", "Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Company Creation", "EBS Product Creation", "EBS Cross Validation Creation", "EBS Team Creation", "EBS Department Creation", "EBS Account Creation", "EBS Location Creation", "HFM Product Creation", "HFM Location Creation", "HFM Company Creation", "HFM Cross Validation Creation", "HFM Team Creation", "HFM Account Creation", "HFM Department Creation", "SSL Team Creation", "Salesforce Team Creation", "Service Desk Team Creation", "HR Location Creation", "HR Team Creation", "HR Department Creation", "HR Company Creation", "Done"]

(compared using eql?)
 (RSpec::Expectations::ExpectationNotMetError)
    ./lib/world/helper/service_desk_helper.rb:317:in `validate_pizza_tracker_values_for_fst_request'
./features/step_definitions/sd_request_steps.rb:587:in `/^([^"]*) Resubmits the FST ([^"]*) request$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_department_request.feature:17:in `And RackerFST7 Resubmits the FST Department request'
./lib/world/helper/service_desk_helper.rb:317:in `validate_pizza_tracker_values_for_fst_request'
./features/step_definitions/sd_request_steps.rb:587:in `/^([^"]*) Resubmits the FST ([^"]*) request$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_department_request.feature:17:in `And RackerFST7 Resubmits the FST Department request'
./lib/world/helper/service_desk_helper.rb:317:in `validate_pizza_tracker_values_for_fst_request'
./features/step_definitions/sd_request_steps.rb:587:in `/^([^"]*) Resubmits the FST ([^"]*) request$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_department_request.feature:17:in `And RackerFST7 Resubmits the FST Department request'
    315  def validate_pizza_tracker_values_for_fst_request(request_type)
316    @page = FSTRequestedItemPage.new
317    expect(@page.pizza_length.text.split("\n")).to eql(SD_Form_Validation["FST_Pizza_Tracker_#{request_type}"])
318    puts "Pizza Tracker values for #{request_type} displayed #{@page.pizza_length.text.split("\n")} as expected"
319  end
  13. And Once All the FST Approvals and Tasks are closed
    features/step_definitions/sd_request_steps.rb:591
  14. Then As a RackerFST7 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
    15. Screenshot
     
@regression @module1 @sd @brm @new_fst

Feature: Service Desk BRM - FST Request - Location

Background

  1. Given I login as a RackerFST3
    features/step_definitions/global_steps.rb:1
@fst_locationfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:7

Scenario: New FST Flexfield - Location Request - E2E Flow

  1. When I create a New Flexfield Request - Location BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Location - FIN0001487
  3. Pizza Tracker values for Location displayed ["Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Location Creation", "HFM Location Creation", "HR Location Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending Fin. Reporting Approval as expected
  5. And once the FRT, FRD Approves the BRM FST request
    features/step_definitions/sd_request_steps.rb:113
  6. Alert Message for Location dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Location #" on Request ( Edit Location button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  7. FST_FRT_Approver - Approved the Request
  8. FRD - Approved the Request
  9. And as a Technician I validate EBS, HFM, HR FST-Tasks and close each request
    features/step_definitions/sd_request_steps.rb:91
  10. EBS FlexField Task # : TASK0115708
  11. HFM FlexField Task # : TASK0115709
  12. HR FlexField Task # : HR0069005
  13. Then As a RackerFST3 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  14. Current Pizza Tracker stage displayed Done as expected
@fst_location_rejectfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:14

Scenario: New FST Flexfield - Location Request - SEC Director Reject and Racker Resubmission - E2E Flow

  1. When I create a New Flexfield Request - Location BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Location - FIN0001488
  3. Pizza Tracker values for Location displayed ["Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Location Creation", "HFM Location Creation", "HR Location Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending Fin. Reporting Approval as expected
  5. And As a Financial Reporting Director I Reject the request
    features/step_definitions/sd_request_steps.rb:562
  6. Alert Message for Location dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Location #" on Request ( Edit Location button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  7. FST_FRT_Approver - Approved the Request
  8. FRD - Rejecting the Request
  9. And RackerFST3 Resubmits the FST Location request
    features/step_definitions/sd_request_steps.rb:576
  10. Pizza Tracker does not highlight any stage for Rejected request
  11. Stage displayed 'Rejected' as expected
  12. Pizza Tracker values for Location displayed ["Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Location Creation", "HFM Location Creation", "HR Location Creation", "Done"] as expected
  13. And Once All the FST Approvals and Tasks are closed
    features/step_definitions/sd_request_steps.rb:591
    expected true
     got nil
 (RSpec::Expectations::ExpectationNotMetError)
    ./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
./lib/world/helper/service_desk_helper.rb:1166:in `navigate_to_my_approvals_page_by_fst_frt_and_search'
./lib/world/helper/service_desk_helper.rb:180:in `update_fst_details_and_approve_by_frt'
./lib/world/helper/service_desk_helper.rb:176:in `approve_fst_request_as_a_frt_approver'
./lib/world/helper/service_desk_helper.rb:171:in `block in approve_fst_request_on_my_approvals_page'
./lib/world/helper/service_desk_helper.rb:169:in `each'
./lib/world/helper/service_desk_helper.rb:169:in `approve_fst_request_on_my_approvals_page'
./features/step_definitions/sd_request_steps.rb:114:in `/^once the ([^"]*) Approves the BRM FST request$/'
./features/step_definitions/sd_request_steps.rb:608:in `/^Once All the FST Approvals and Tasks are closed$/'
features/service_desk_module/service_desk_brm_module/fst_request/fst_location_request.feature:18:in `And Once All the FST Approvals and Tasks are closed'
    1164    @page.request_number_search.value = "*#{@ritm_number}"
1165    @page.request_number_search.send_keys :enter
1166    expect(@page.myapprovals_table_firstcell.visible?).to be true
1167    fail 'Table has not had any data. ' if @page.my_approver_table.rows.empty?
1168    @page.myapprovals_table_firstcell.click
  14. Then As a RackerFST3 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
    15. Screenshot
     
@regression @module1 @sd @brm @new_fst

Feature: Service Desk BRM - FST Request - Product

Background

  1. Given I login as a RackerFST5
    features/step_definitions/global_steps.rb:1
@fst_productfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_product_request.feature:7

Scenario: New FST Flexfield - Product Request - E2E Flow

  1. When I create a New Flexfield Request - Product BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Product - FIN0001489
  3. Pizza Tracker values for Product displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Product Creation", "HFM Product Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending FPNA Approval as expected
  5. And once the FPNA, FRT, FRD Approves the BRM FST request
    features/step_definitions/sd_request_steps.rb:113
  6. FPNA - Approved the Request
  7. Alert Message for Product dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Product #" on Request ( Edit Product button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  8. FST_FRT_Approver - Approved the Request
  9. FRD - Approved the Request
  10. And as a Technician I validate EBS, HFM FST-Tasks and close each request
    features/step_definitions/sd_request_steps.rb:91
  11. EBS FlexField Task # : TASK0115710
  12. HFM FlexField Task # : TASK0115711
  13. Then As a RackerFST5 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  14. Current Pizza Tracker stage displayed Done as expected
@fst_product_rejectfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_product_request.feature:14

Scenario: New FST Flexfield - Product Request - SEC Director Reject and Racker Resubmission - E2E Flow

  1. When I create a New Flexfield Request - Product BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Product - FIN0001490
  3. Pizza Tracker values for Product displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Product Creation", "HFM Product Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending FPNA Approval as expected
  5. And As a Financial Reporting Director I Reject the request
    features/step_definitions/sd_request_steps.rb:562
  6. FPNA - Approved the Request
  7. Alert Message for Product dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Product #" on Request ( Edit Product button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  8. FST_FRT_Approver - Approved the Request
  9. FRD - Rejecting the Request
  10. And RackerFST5 Resubmits the FST Product request
    features/step_definitions/sd_request_steps.rb:576
  11. Pizza Tracker does not highlight any stage for Rejected request
  12. Stage displayed 'Rejected' as expected
  13. Pizza Tracker values for Product displayed ["Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Product Creation", "HFM Product Creation", "Done"] as expected
  14. And Once All the FST Approvals and Tasks are closed
    features/step_definitions/sd_request_steps.rb:591
  15. FPNA - Approved the Request
  16. Alert Message for Product dispayed as expected - 'It is mandatory for the 1st Financial Reporting Approver to populate the "Product #" on Request ( Edit Product button) that will be used in Oracle and downstream systems. This needs to be entered prior to approval.'
  17. FST_FRT_Approver - Approved the Request
  18. FRD - Approved the Request
  19. EBS FlexField Task # : TASK0115712
  20. HFM FlexField Task # : TASK0115713
  21. Then As a RackerFST5 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  22. Current Pizza Tracker stage displayed Done as expected
@regression @module1 @sd @brm @new_fst

Feature: Service Desk BRM - FST Request - Team

Background

  1. Given I login as a RackerFST1
    features/step_definitions/global_steps.rb:1
@fst_teamfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_team_request.feature:7

Scenario: New FST Flexfield - TEAM Request E2E Flow

  1. When I create a New Flexfield Request - Team BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Team - FIN0001491
  3. Pizza Tracker values for Team displayed ["Pending Finance Partner Approval", "Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Team Creation", "HFM Team Creation", "SSL Team Creation", "Salesforce Team Creation", "Service Desk Team Creation", "HR Team Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending Finance Partner Approval as expected
  5. And once the FP, FPNA, FRT, FRD Approves the BRM FST request
    features/step_definitions/sd_request_steps.rb:113
  6. FP - Approved the Request
  7. FPNA - Approved the Request
  8. Alert Message for Team dispayed as expected - 'It is mandatory for the Financial Reporting Approver to populate the Team ID on Request ( Edit Team ID button) that will be used in Oracle and downstream systems. This needs to be inputted prior to approval.'
  9. FST_FRT_Approver - Approved the Request
  10. FRD - Approved the Request
  11. And as a Technician I validate EBS, HFM, SSL FST-Tasks and close each request
    features/step_definitions/sd_request_steps.rb:91
  12. EBS FlexField Task # : TASK0115714
  13. HFM FlexField Task # : TASK0115715
  14. SSL FlexField Task # : TASK0115716
  15. And as a Technician I validate SalesForce, ServiceDesk, HR FST-Tasks and close each request
    features/step_definitions/sd_request_steps.rb:91
  16. SalesForce FlexField Task # : TASK0115717
  17. ServiceDesk FlexField Task # : TASK0115718
  18. HR FlexField Task # : HR0069006
  19. Then As a RackerFST1 I validate that the BRM-FST request is in Done Stage
    features/step_definitions/sd_request_steps.rb:286
  20. Current Pizza Tracker stage displayed Done as expected
@fst_team_rejectfeatures/service_desk_module/service_desk_brm_module/fst_request/fst_team_request.feature:15

Scenario: New FST Flexfield - TEAM Request - SEC Director Reject and Racker Resubmission with addtional team - E2E Flow

  1. When I create a New Flexfield Request - Team BRM-FST-request
    features/step_definitions/sd_request_steps.rb:558
  2. FST # for Team - FIN0001492
  3. Pizza Tracker values for Team displayed ["Pending Finance Partner Approval", "Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Team Creation", "HFM Team Creation", "SSL Team Creation", "Salesforce Team Creation", "Service Desk Team Creation", "HR Team Creation", "Done"] as expected
  4. Current Pizza Tracker stage displayed Pending Finance Partner Approval as expected
  5. And As a Financial Reporting Director I Reject the request
    features/step_definitions/sd_request_steps.rb:562
  6. FP - Approved the Request
  7. FPNA - Approved the Request
  8. Alert Message for Team dispayed as expected - 'It is mandatory for the Financial Reporting Approver to populate the Team ID on Request ( Edit Team ID button) that will be used in Oracle and downstream systems. This needs to be inputted prior to approval.'
  9. FST_FRT_Approver - Approved the Request
  10. FRD - Rejecting the Request
  11. And RackerFST1 Resubmits the FST Team request
    features/step_definitions/sd_request_steps.rb:576
  12. Pizza Tracker does not highlight any stage for Rejected request
  13. Stage displayed 'Rejected' as expected
  14. Pizza Tracker values for Team displayed ["Pending Finance Partner Approval", "Pending FPNA Approval", "Pending Fin. Reporting Approval", "Pending Fin. Reporting Director Approval", "EBS Team Creation", "HFM Team Creation", "SSL Team Creation", "Salesforce Team Creation", "Service Desk Team Creation", "HR Team Creation", "Done"] as expected
  15. And Once All the FST Approvals and Tasks are closed
    features/step_definitions/sd_request_steps.rb:591
  16. FP - Approved the Request
  17. FPNA - Approved the Request
  18. Alert Message for Team dispayed as expected - 'It is mandatory for the Financial Reporting Approver to populate the Team ID on Request ( Edit Team ID button) that will be used in Oracle and downstream systems. This needs to be inputted prior to approval.'
  19. FST_FRT_Approver - Approved the Request
  20. FRD - Approved the Request
  21. EBS FlexField Task # : TASK0115719
  22. HFM FlexField Task # : TASK0115720
  23. SSL FlexField Task # : TASK0115721
  24. SalesForce FlexField Task # : TASK0115722
  25. ServiceDesk FlexField Task # : TASK0115723
  26. HR FlexField Task # : HR0069007
  27. Then As a RackerFST1 I validate that the BRM-FST request is in Done Stage for Resubmited request
    features/step_definitions/sd_request_steps.rb:295
  28. Current Pizza Tracker stage displayed Done as expected
@regression @module1 @sd @brm @brm_hel

Feature: Service Desk BRM - Oracle Incidents

Background

  1. Given I login as a RackerBrm4
    features/step_definitions/global_steps.rb:1
features/service_desk_module/service_desk_brm_module/incident/oracle_incidents.feature:6

Scenario: Creation of Oracle - EBS Issue by Racker and validation of Task by SD Tech

  1. When I create a Oracle - EBS Issue BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Incident number ---- INC0285788
  3. Then As a SDTechnician I should see Incident for Oracle - EBS Issue Task generated
    features/step_definitions/sd_incident_steps.rb:23
  4. Task Number : INC0285788
  5. Assignment Group : Oracle - EBS
  6. Category : SW - 3rd Party Enterprise Applications
  7. Sub-Category : Oracle-EBS Troubleshooting
  8. Sub-subCategory : AP - Accounts Payables
features/service_desk_module/service_desk_brm_module/incident/oracle_incidents.feature:10

Scenario: Creation of Global Sales & Contract Systems issue by Racker and validation of Task by SD Tech

  1. When I create a Global Sales & Contract Systems Issue BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Incident number ---- INC0285789
  3. Then As a SDTechnician I should see Incident for Global Sales & Contract Systems Issue Task generated
    features/step_definitions/sd_incident_steps.rb:23
  4. Task Number : INC0285789
  5. Assignment Group : GSCS DevOps
  6. Category : SW - Rackspace Products
  7. Sub-Category : Doc Depot
  8. Sub-subCategory : Other
@sraifeatures/service_desk_module/service_desk_brm_module/incident/oracle_incidents.feature:15

Scenario: Creation of Submit Revenue Assurance Issue by Racker and validation of Task by SD Tech

  1. When I create a Submit Revenue Assurance Issue BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Incident number ---- INC0285790
  3. Then As a SDTechnician I should see Incident for Submit Revenue Assurance Issue Task generated
    features/step_definitions/sd_incident_steps.rb:23
  4. Task Number : INC0285790
  5. Assignment Group : Revenue Assurance
  6. Category : SW - Rackspace Products
  7. Sub-Category : Revenue Assurance
  8. Sub-subCategory : Other
@regression @module1 @sd @brm @brm_hel

Feature: BRM - BRM ESS and Request Page Form Validation

Background

  1. Given I login as a RackerBrm1
    features/step_definitions/global_steps.rb:1
features/service_desk_module/service_desk_brm_module/request/brm_ess_and_request_page_validation.feature:6

Scenario: Validation of FST, BRM/Oracle (Request, Incidents), Utility Grid, Polaris-Intake on BRM ESS

  1. And I am on BRM Employee Self-Service portal page
    features/step_definitions/sd_request_steps.rb:527
  2. Then I should see the FST, BRM/Oracle (Request, Incidents), Utility Grid, Polaris-Intake on BRM ESS section on ESS page
    features/step_definitions/sd_request_steps.rb:531
  3. FST Request Links: ["Financial Systems Team - Request", "New Flexfield Request - Company", "New Flexfield Request - Location", "New Flexfield Request - Account", "New Flexfield Request - Team", "New Flexfield Request - Department", "New Flexfield Request - Product", "Change Flexfield Request - Rename", "Change Flexfield Request - Disable", "Submit a Security Rule Request", "Submit a Cross Validation Request", "Submit a HFM Request"]
  4. BRM Requests Links: ["BRM-Requests", "Access & Permissions Request", "Analysis Request", "Operational Request", "New Environment Request", "BRM Price Change Request", "Minimum Support Waive", "BRM DvC Account Creation", "Submit Revenue Assurance Issue", "Usage Request"]
  5. BRM Incidents Links: ["BRM-Incidents", "Report a BRM Issue", "Report a UMS Issue"]
  6. Utility Grid Links: ["Utility Grid", "Billing Stack Request", "Submit a Billing Stack Issue"]
  7. Polaris Intake Links: ["Polaris-Intake", "Polaris Intake Request"]
  8. Oracle Requests Links: ["Oracle Requests", "Oracle - EBS Request", "Global Sales & Contract Systems Request"]
  9. Oracle Incidents Links: ["Oracle Incidents", "Oracle - EBS Issue", "Global Sales & Contract Systems Issue"]
  10. My Open Items Links: ["Open Orders", "Open Incidents", "My Approvals", "My FST Tickets", "Closed Tickets"]
@brm_test1features/service_desk_module/service_desk_brm_module/request/brm_ess_and_request_page_validation.feature:11

Scenario: Validation of Location and Order list DD values on Catalog Item - Mobile Device page

  1. And I am on BRM-Portal > Catalog Item - Access & Permissions Request Page
    features/step_definitions/sd_request_steps.rb:477
  2. Then I should see the dropdown fields and values on BRM Catalog Item - Access & Permissions Request page
    features/step_definitions/sd_request_steps.rb:537
  3. Priority dropdown values : ["-- None --", "P1 - Critical", "P2 - High", "P3 - Medium", "P4 - Low"]
  4. Type of Access dropdown values : ["-- None --", "Environment", "Application", "Other"]
  5. Access Type dropdown values : ["-- None --", "Add", "Remove"]
  6. And the BRM Access & Permissions Request page form displayed based on the type of access selection
    features/step_definitions/sd_request_steps.rb:547
  7. The following elements ["txt_what_is_the_reason_for_the_access", "txt_what_environment_do_you_need_access_to", "txt_what_is_the_pin_user", "txt_who_is_the_environment_owner", "dd_length_of_time_needed"] displayed expected when 'What type of access do you need? is Environment'
  8. The following elements ["chk_business_intelligence_publisher", "chk_customer_center", "chk_payment_center", "chk_pricing_center", "chk_billing_processor_bip", "chk_operations", "chk_read_only"] displayed expected when 'What type of access do you need? is Application'
@regression @module1 @sd @brm @brm_hel

Feature: Service Desk BRM - BRM Requests

Background

  1. Given I login as a RackerBrm1
    features/step_definitions/global_steps.rb:1
@analysis_requestfeatures/service_desk_module/service_desk_brm_module/request/brm_request.feature:7

Scenario: Creation of Analysis Request by Racker and validation of Task by SD Tech

  1. When I create a Analysis Request BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Request Number : RITM0106244
  3. Then As a SDTechnician I should see the Analysis Request Task generated
    features/step_definitions/sd_request_steps.rb:61
  4. Task Number : TASK0115724
  5. Assignment Group : App Support - BRM
  6. Category : SW - 3rd Party Enterprise Applications
  7. Sub-Category : BRM Analysis
  8. Sub-subCategory : null
@operational_requestfeatures/service_desk_module/service_desk_brm_module/request/brm_request.feature:12

Scenario: Creation of Operational Request by Racker and validation of Task by SD Tech

  1. When I create a Operational Request BRM-request
    features/step_definitions/sd_request_steps.rb:30
    Element with locator <xpath='//tr[contains(@class,'io_label')][contains(.,'Priority')]/following-sibling::tr[*]/td[*]/span/select[@class='cat_item_option']'> not found (Merlot::MissingElementError)
    ./lib/world/helper/service_desk_helper.rb:46:in `block in create_sd_request'
./lib/world/helper/service_desk_helper.rb:41:in `create_sd_request'
./features/step_definitions/sd_request_steps.rb:36:in `/^I create a ([\w ].+) BRM-request$/'
features/service_desk_module/service_desk_brm_module/request/brm_request.feature:13:in `When I create a Operational Request BRM-request'
./lib/world/helper/service_desk_helper.rb:46:in `block in create_sd_request'
./lib/world/helper/service_desk_helper.rb:41:in `create_sd_request'
./features/step_definitions/sd_request_steps.rb:36:in `/^I create a ([\w ].+) BRM-request$/'
features/service_desk_module/service_desk_brm_module/request/brm_request.feature:13:in `When I create a Operational Request BRM-request'
./lib/world/helper/service_desk_helper.rb:46:in `block in create_sd_request'
./lib/world/helper/service_desk_helper.rb:41:in `create_sd_request'
./features/step_definitions/sd_request_steps.rb:36:in `/^I create a ([\w ].+) BRM-request$/'
features/service_desk_module/service_desk_brm_module/request/brm_request.feature:13:in `When I create a Operational Request BRM-request'
./lib/world/helper/service_desk_helper.rb:46:in `block in create_sd_request'
./lib/world/helper/service_desk_helper.rb:41:in `create_sd_request'
./features/step_definitions/sd_request_steps.rb:36:in `/^I create a ([\w ].+) BRM-request$/'
features/service_desk_module/service_desk_brm_module/request/brm_request.feature:13:in `When I create a Operational Request BRM-request'
    44          page[element].click
45        else
46          page[element] = value
47        end
48    } unless request_name.eql? 'Bring my number to rackspace'
  2. And once the Rackers Manager Approves the request
    features/step_definitions/sd_request_steps.rb:107
  3. Then As a SDTechnician I should see the Operational Request Task generated
    features/step_definitions/sd_request_steps.rb:61
    4. Screenshot
     
@brm_request_slafeatures/service_desk_module/service_desk_brm_module/request/brm_request.feature:18

Scenario: Creation of New Environment Request by Racker and validation of Task by SD Tech

  1. When I create a New Environment Request BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Request Number : RITM0106245
  3. And once the Rackers Manager Approves the request
    features/step_definitions/sd_request_steps.rb:107
  4. Then As a SDTechnician I should see the New Environment Request Task generated
    features/step_definitions/sd_request_steps.rb:61
  5. Task Number : TASK0115725
  6. Assignment Group : BillingDevOps
  7. Category : SW - 3rd Party Enterprise Applications
  8. Sub-Category : BRM Environment Deployment
  9. Sub-subCategory : null
@minimum_support_requestfeatures/service_desk_module/service_desk_brm_module/request/brm_request.feature:24

Scenario: Creation of Minimum Support Waive by Racker and validation of Task by SD Tech

  1. When I create a Minimum Support Waive BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Request Number : RITM0106246
  3. And once the Rackers Manager Approves the request
    features/step_definitions/sd_request_steps.rb:107
  4. And once the PolarisReviewer Approves the request
    features/step_definitions/sd_request_steps.rb:222
  5. Then As a SDTechnician I should see the Minimum Support Waive Task generated
    features/step_definitions/sd_request_steps.rb:61
  6. Task Number : TASK0115726
  7. Assignment Group : App Support - BRM
  8. Category : SW - 3rd Party Enterprise Applications
  9. Sub-Category : BRM Pricing
  10. Sub-subCategory : Price Change
@dvc_account_requestfeatures/service_desk_module/service_desk_brm_module/request/brm_request.feature:31

Scenario: Creation of BRM DvC Account Creation by Racker and validation of Task by SD Tech

  1. When I create a BRM DvC Account Creation BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Request Number : RITM0106247
  3. Then As a SDTechnician I should see the BRM DvC Account Creation Task generated
    features/step_definitions/sd_request_steps.rb:61
  4. Task Number : TASK0115727
  5. Assignment Group : App Support - BRM
  6. Category : SW - 3rd Party Enterprise Applications
  7. Sub-Category : BRM Operational
  8. Sub-subCategory : DvC Setup
@usage_requestfeatures/service_desk_module/service_desk_brm_module/request/brm_request.feature:36

Scenario: Creation of Usage Request by Racker and validation of Task by SD Tech

  1. When I create a Usage Request BRM-request
    features/step_definitions/sd_request_steps.rb:30
    Element with locator <css='.outputmsg_text'> not found (Merlot::MissingElementError)
    ./lib/world/helper/service_desk_helper.rb:706:in `continue_shopping_cart_and_ordersummary'
./lib/world/helper/service_desk_helper.rb:84:in `confirm_brm_order'
./features/step_definitions/sd_request_steps.rb:37:in `/^I create a ([\w ].+) BRM-request$/'
features/service_desk_module/service_desk_brm_module/request/brm_request.feature:37:in `When I create a Usage Request BRM-request'
./lib/world/helper/service_desk_helper.rb:706:in `continue_shopping_cart_and_ordersummary'
./lib/world/helper/service_desk_helper.rb:84:in `confirm_brm_order'
./features/step_definitions/sd_request_steps.rb:37:in `/^I create a ([\w ].+) BRM-request$/'
features/service_desk_module/service_desk_brm_module/request/brm_request.feature:37:in `When I create a Usage Request BRM-request'
./lib/world/helper/service_desk_helper.rb:706:in `continue_shopping_cart_and_ordersummary'
./lib/world/helper/service_desk_helper.rb:84:in `confirm_brm_order'
./features/step_definitions/sd_request_steps.rb:37:in `/^I create a ([\w ].+) BRM-request$/'
features/service_desk_module/service_desk_brm_module/request/brm_request.feature:37:in `When I create a Usage Request BRM-request'
./lib/world/helper/service_desk_helper.rb:706:in `continue_shopping_cart_and_ordersummary'
./lib/world/helper/service_desk_helper.rb:84:in `confirm_brm_order'
./features/step_definitions/sd_request_steps.rb:37:in `/^I create a ([\w ].+) BRM-request$/'
features/service_desk_module/service_desk_brm_module/request/brm_request.feature:37:in `When I create a Usage Request BRM-request'
    704        # @page.submit_order.click
705    @page = OrderStatusPage.new
706    expect(@page[:order_status_message].text).to eql(GLOBALCONF['order_status_page']['order_status_thankyou_message'])
707  end
  2. Then As a SDTechnician I should see the Usage Request Task generated
    features/step_definitions/sd_request_steps.rb:61
    3. Screenshot
     
@regression @module1 @sd @brm @sd_e2e @brm_e2e

Feature: Service Desk BRM - Creation of BRM Request - With NO Manager Approval required - End to End Flow

Background

  1. Given I login as a BRM
    features/step_definitions/global_steps.rb:1
  2. And I create a Oracle - EBS Request BRM-request
    features/step_definitions/sd_request_steps.rb:30
  3. Request Number : RITM0106248
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:7

Scenario: Creation of a BRM Request by Racker and validation of Requested Item Page for default values

  1. Then I should see the Request Created on ESS Requested Item Page
    features/step_definitions/sd_request_steps.rb:70
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:10

Scenario: Service Desk Technician assigns the new request and places the request on hold

  1. When I login as SDTechnician
    features/step_definitions/sd_request_steps.rb:190
  2. And I validate the Category and Assignment for BRM group
    features/step_definitions/sd_request_steps.rb:205
  3. Task Number - TASK0115729
  4. And I set the Task on Hold
    features/step_definitions/sd_request_steps.rb:194
    Element not found in the cache - perhaps the page has changed since it was looked up (Selenium::WebDriver::Error::StaleElementReferenceError)
    [remote server] resource://fxdriver/modules/web-element-cache.js:9454:in `fxdriver.cache.getElementAt'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:9039:in `Utils.getElementAt'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12173:in `WebElement.isElementSelected'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12661:in `DelayedCommand.prototype.executeInternal_/h'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12666:in `DelayedCommand.prototype.executeInternal_'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12608:in `DelayedCommand.prototype.execute/<'
[remote server] resource://fxdriver/modules/web-element-cache.js:9454:in `fxdriver.cache.getElementAt'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:9039:in `Utils.getElementAt'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12173:in `WebElement.isElementSelected'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12661:in `DelayedCommand.prototype.executeInternal_/h'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12666:in `DelayedCommand.prototype.executeInternal_'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12608:in `DelayedCommand.prototype.execute/<'
./lib/world/helper/service_desk_helper.rb:437:in `validate_status_on_catalog_page'
./features/step_definitions/sd_request_steps.rb:197:in `/^I set the Task on Hold$/'
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:13:in `And I set the Task on Hold'
[remote server] resource://fxdriver/modules/web-element-cache.js:9454:in `fxdriver.cache.getElementAt'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:9039:in `Utils.getElementAt'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12173:in `WebElement.isElementSelected'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12661:in `DelayedCommand.prototype.executeInternal_/h'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12666:in `DelayedCommand.prototype.executeInternal_'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12608:in `DelayedCommand.prototype.execute/<'
./lib/world/helper/service_desk_helper.rb:437:in `validate_status_on_catalog_page'
./features/step_definitions/sd_request_steps.rb:197:in `/^I set the Task on Hold$/'
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:13:in `And I set the Task on Hold'
[remote server] resource://fxdriver/modules/web-element-cache.js:9454:in `fxdriver.cache.getElementAt'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:9039:in `Utils.getElementAt'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12173:in `WebElement.isElementSelected'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12661:in `DelayedCommand.prototype.executeInternal_/h'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12666:in `DelayedCommand.prototype.executeInternal_'
[remote server] file:///var/folders/4_/hhzjw6g97493918sphkwxxp0j_23y7/T/webdriver-profile20160805-23487-67vn8s/extensions/fxdriver@googlecode.com/components/command-processor.js:12608:in `DelayedCommand.prototype.execute/<'
./lib/world/helper/service_desk_helper.rb:437:in `validate_status_on_catalog_page'
./features/step_definitions/sd_request_steps.rb:197:in `/^I set the Task on Hold$/'
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:13:in `And I set the Task on Hold'
    9452# Couldn't get snippet for [remote server] resource://fxdriver/modules/web-element-cache.js
  5. Then I should see the Task Status as On Hold
    features/step_definitions/sd_request_steps.rb:201
    6. Screenshot
     
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:16

Scenario: Racker responds to the request that is placed on Hold by Service Desk Technician

  1. And I am on My Orders details page with On Hold request
    features/step_definitions/sd_request_steps.rb:215
  2. When I update the On Hold Additional comments
    features/step_definitions/sd_request_steps.rb:236
  3. Then I should see the On Hold Additional comments updated
    features/step_definitions/sd_request_steps.rb:240
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:21

Scenario: Service Desk Technician places the request on RAN

  1. When I login as SDTechnician
    features/step_definitions/sd_request_steps.rb:190
  2. And I navigate to My Group Work link
    features/step_definitions/sd_request_steps.rb:254
  3. And I set the Task on RAN
    features/step_definitions/sd_request_steps.rb:244
  4. Then I should see the Task Status as RAN
    features/step_definitions/sd_request_steps.rb:250
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:27

Scenario: Service Desk Technician places the request on RVN

  1. When I login as SDTechnician
    features/step_definitions/sd_request_steps.rb:190
  2. And I navigate to My Group Work link
    features/step_definitions/sd_request_steps.rb:254
  3. And I set the Task on RVN
    features/step_definitions/sd_request_steps.rb:258
  4. Then I should see the Task Status as RVN
    features/step_definitions/sd_request_steps.rb:264
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:33

Scenario: Racker closes the request that is placed on RVN by Service Desk Technician

  1. And I am on My Orders details page with RVN request
    features/step_definitions/sd_request_steps.rb:228
  2. When I update and close the RVN Request
    features/step_definitions/sd_request_steps.rb:268
  3. Then I should see the request on My Closed Orders page
    features/step_definitions/sd_request_steps.rb:272
@brm_e2e1features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:39

Scenario: Service Desk Technician updates the closing comment for the request that is closed by Racker

  1. And I close the RVN request
    features/step_definitions/sd_request_steps.rb:303
  2. When I login as SDTechnician
    features/step_definitions/sd_request_steps.rb:190
  3. And I update the Closed by Requester Additional comments
    features/step_definitions/sd_request_steps.rb:308
  4. Task # ---TASK0115734
  5. Then I should see the Activity log updated
    features/step_definitions/sd_request_steps.rb:326
features/service_desk_module/service_desk_brm_module/request/brm_request_end_to_end_no_mgr_approval.feature:45

Scenario: Racker validates the closed request under the self service

  1. And I perform End to End request
    features/step_definitions/sd_request_steps.rb:332
  2. Task # ---TASK0115735
  3. When I am on Self Service Closed Requested Item page
    features/step_definitions/sd_request_steps.rb:351
  4. Then I should see the request state updated to Closed
    features/step_definitions/sd_request_steps.rb:356
@regression @module1 @sd @brm @brm_hel

Feature: Service Desk BRM - Oracle Requests

Background

  1. Given I login as a RackerBrm3
    features/step_definitions/global_steps.rb:1
@brm_requestfeatures/service_desk_module/service_desk_brm_module/request/oracle_request.feature:7

Scenario: Creation of Oracle - EBS Request by Racker and validation of Task by SD Tech

  1. When I create a Oracle - EBS Request BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Request Number : RITM0106256
  3. Then As a SDTechnician I should see the Oracle - EBS Request Task generated
    features/step_definitions/sd_request_steps.rb:61
  4. Task Number : TASK0115736
  5. Assignment Group : Oracle - EBS
  6. Category : SW - 3rd Party Enterprise Applications
  7. Sub-Category : Oracle-EBS Extension
  8. Sub-subCategory : AP - Accounts Payables
@brm_requestfeatures/service_desk_module/service_desk_brm_module/request/oracle_request.feature:12

Scenario: Creation of Global Sales & Contract Systems Request by Racker and validation of Task by SD Tech

  1. When I create a Global Sales & Contract Systems Request BRM-request
    features/step_definitions/sd_request_steps.rb:30
  2. Request Number : RITM0106257
  3. Then As a SDTechnician I should see the Global Sales & Contract Systems Request Task generated
    features/step_definitions/sd_request_steps.rb:61
  4. Task Number : TASK0115737
  5. Assignment Group : GSCS DevOps
  6. Category : SW - Rackspace Products
  7. Sub-Category : Proposal Manager
  8. Sub-subCategory : Application Configuration
@regression @module1 @sd @brm @sla_validation

Feature: Service Desk SLA Validation

Background

  1. Given I login as a SDTechnician
    features/step_definitions/global_steps.rb:1
@sla_incfeatures/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:7

Scenario Outline: SLA Testing for Incident - Asignment Group GET Ops Tier1

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:8
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:9
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:10
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:11
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:12
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:13

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Incident
GET Ops Tier1
1
15 Minutes
1 Hour or 59 Minutes
24x7
24x7
Get Ops Tier 1 P1 INT ACK SLA
Get Ops Tier 1 P1 INT Resolution SLA
Incident Ticket Number # INC0285791, *** AK SLA ***, Name - Get Ops Tier 1 P1 INT ACK SLA , Duration - 14 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Get Ops Tier 1 P1 INT Resolution SLA , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
GET Ops Tier1
2
30 Minutes
4 Hours or 3 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P2 INT Ack SLA
Get Ops Tier 1 P2 INT Resolution SLA
Incident Ticket Number # INC0285792, *** AK SLA ***, Name - Get Ops Tier 1 P2 INT Ack SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Get Ops Tier 1 P2 INT Resolution SLA , Duration - 3 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
GET Ops Tier1
3
30 Minutes
12 Hours or 11 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P3 INT ACK SLA
Get Ops Tier 1 P3 INT Resolution SLA
Incident Ticket Number # INC0285793, *** AK SLA ***, Name - Get Ops Tier 1 P3 INT ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Get Ops Tier 1 P3 INT Resolution SLA , Duration - 11 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
GET Ops Tier1
4
1 Hour or 59 Minutes
1 Day or 23 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P4 INT ACK SLA
Get Ops Tier 1 P4 INT Resolution SLA
Incident Ticket Number # INC0285794, *** AK SLA ***, Name - Get Ops Tier 1 P4 INT ACK SLA , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Get Ops Tier 1 P4 INT Resolution SLA , Duration - 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
GET Ops Tier1
5
1 Hour or 59 Minutes
3 Days or 1 Day or 23 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P5 INT ACK SLA
Get Ops Tier 1 P5 INT Resolution SLA
Incident Ticket Number # INC0285795
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:21:in `And I validate the default Get Ops Tier 1 P5 INT ACK SLA, 1 Hour or 59 Minutes, 24x7 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:9:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_inc11features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:25

Scenario Outline: SLA Testing for Incident - Asignment Group GSCS DevOps

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:26
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:27
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:28
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:29
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:30
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:31

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Incident
GSCS DevOps
1
15 Minutes
1 Hour or 59 Minutes
8x5
8x5
Global Sales & Contract Systems P1 INT A...
Global Sales & Contract Systems P1 INT R...
Incident Ticket Number # INC0285796, *** AK SLA ***, Name - Global Sales & Contract Systems P1 INT A... , Duration - 15 Minutes , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Global Sales & Contract Systems P1 INT R... , Duration - 1 Hour , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
GSCS DevOps
2
30 Minutes
4 Hours or 3 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P2 INT A...
Global Sales & Contract Systems P2 INT R...
Incident Ticket Number # INC0285797, *** AK SLA ***, Name - Global Sales & Contract Systems P2 INT A... , Duration - 30 Minutes , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Global Sales & Contract Systems P2 INT R... , Duration - 4 Hours , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
GSCS DevOps
3
30 Minutes
12 Hours or 11 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P3 INT A...
Global Sales & Contract Systems P3 INT R...
Incident Ticket Number # INC0285798, *** AK SLA ***, Name - Global Sales & Contract Systems P3 INT A... , Duration - 30 Minutes , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Global Sales & Contract Systems P3 INT R... , Duration - 12 Hours , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
GSCS DevOps
4
1 Hour or 59 Minutes
1 Day or 23 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P4 INT A...
Global Sales & Contract Systems P4 INT R...
Incident Ticket Number # INC0285800, *** AK SLA ***, Name - Global Sales & Contract Systems P4 INT A... , Duration - 1 Hour , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Global Sales & Contract Systems P4 INT R... , Duration - 1 Day , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
GSCS DevOps
5
1 Hour or 59 Minutes
2 Days or 1 Day 23 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P5 INT A...
Global Sales & Contract Systems P5 INT R...
Incident Ticket Number # INC0285801
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:39:in `And I validate the default Global Sales & Contract Systems P5 INT A..., 1 Hour or 59 Minutes, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:27:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_incfeatures/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:43

Scenario Outline: SLA Testing for Incident - Asignment Group Racker Experience

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:44
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:45
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:46
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:47
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:48
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:49

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Incident
Racker Experience
1
1 Hour or 59 Minutes
2 Hours or 1 Hour 59 Minutes
8x5
8x5
Racker Experience P1 INT ACK SLA
Racker Experience P1 INT Resolution
Incident Ticket Number # INC0285802, *** AK SLA ***, Name - Racker Experience P1 INT ACK SLA , Duration - 1 Hour , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Racker Experience P1 INT Resolution , Duration - 2 Hours , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
Racker Experience
2
1 Hour or 59 Minutes
6 Hours or 5 Hours 59 Minutes
8x5
8x5
Racker Experience P2 INT ACK SLA
Racker Experience P2 INT Resolution
Incident Ticket Number # INC0285803, *** AK SLA ***, Name - Racker Experience P2 INT ACK SLA , Duration - 1 Hour , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Racker Experience P2 INT Resolution , Duration - 6 Hours , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
Racker Experience
3
6 Hours or 5 Hours 59 Minutes
12 Hours or 11 Hours 59 Minutes
8x5
8x5
Racker Experience P3 INT ACK SLA
Racker Experience P3 INT Resolution
Incident Ticket Number # INC0285804, *** AK SLA ***, Name - Racker Experience P3 INT ACK SLA , Duration - 6 Hours , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Racker Experience P3 INT Resolution , Duration - 12 Hours , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
Racker Experience
4
12 Hours or 11 Hours 59 Minutess
2 Days or 1 Day 23 Hours 59 Minutes
8x5
8x5
Racker Experience P4 INT ACK SLA
Racker Experience P4 INT Resolution
Incident Ticket Number # INC0285805, *** AK SLA ***, Name - Racker Experience P4 INT ACK SLA , Duration - 12 Hours , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Racker Experience P4 INT Resolution , Duration - 1 Day , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
Racker Experience
5
2 Days or 1 Day 23 Hours 59 Minutes
3 Days or 2 Days 23 Hours 59 Minutes
8x5
8x5
Racker Experience P5 INT ACK SLA
Racker Experience P5 INT Resolution
Incident Ticket Number # INC0285806
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:57:in `And I validate the default Racker Experience P5 INT ACK SLA, 2 Days or 1 Day 23 Hours 59 Minutes, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:45:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@billdev1features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:60

Scenario Outline: SLA Testing for Incident - Asignment Group BillingDevOps

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:61
  2. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:62
  3. And validate that only one sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:63

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Incident
BillingDevOps
1
N/A
1 Hour or 59 Minutes
N/A
24x7
N/A
Billing DevOps P1 INT Resolution
Incident Ticket Number # INC0285807, *** Res SLA validation***, Name - Billing DevOps P1 INT Resolution , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress
Incident
BillingDevOps
2
N/A
6 Hours or 5 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P2 INT Resolution
Incident Ticket Number # INC0285808, *** Res SLA validation***, Name - Billing DevOps P2 INT Resolution , Duration - 5 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress
Incident
BillingDevOps
3
N/A
12 Hours or 11 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P3 INT Resolution
Incident Ticket Number # INC0285809, *** Res SLA validation***, Name - Billing DevOps P3 INT Resolution , Duration - 11 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress
Incident
BillingDevOps
4
N/A
1 Day or 23 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P4 INT Resolution
Incident Ticket Number # INC0285810, *** Res SLA validation***, Name - Billing DevOps P4 INT Resolution , Duration - 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress
Incident
BillingDevOps
5
N/A
3 Days or 2 Days 23 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P5 INT Resolution
Incident Ticket Number # INC0285811
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:392:in `/^I validate the resolution (.*), (.*), (.*) SLA created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:71:in `And I validate the resolution Billing DevOps P5 INT Resolution, 3 Days or 2 Days 23 Hours 59 Minutes, 24x7 SLA created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla.feature:62:in `And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created'
@regression @module1 @sd @brm @sla_validation

Feature: Service Desk SLA Validation

Background

  1. Given I login as a SDTechnician
    features/step_definitions/global_steps.rb:1
@sla_inc1features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:7

Scenario Outline: SLA Testing for Incident - Asignment Group Automation Services Operations

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:8
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:9
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:10
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:11
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:12
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:13

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Incident
Automation Services Operations
1
1 Hour or 59 Minutes
1 Day or 23 Hours 59 Minutes
24x7
24x7
ASOP P1 Issue In Queue
ASOP P1 Issue Resolution
Incident Ticket Number # INC0285812, *** AK SLA ***, Name - ASOP P1 Issue In Queue , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - ASOP P1 Issue Resolution , Duration - 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
Automation Services Operations
2
2 Hours or 1 Hour 59 Minutes
2 Days or 1 Day 23 Hours 59 Minutes
24x7
24x7
ASOP P2 Issue In Queue
ASOP P2 Issue Resolution
Incident Ticket Number # INC0285813, *** AK SLA ***, Name - ASOP P2 Issue In Queue , Duration - 1 Hour 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - ASOP P2 Issue Resolution , Duration - 1 Day 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
Automation Services Operations
3
4 Hours or 3 Hours 59 Minutes
5 Days or 4 Days 23 Hours 59 Minutes
24x7
24x7
ASOP P3 Issue In Queue
ASOP P3 Issue Resolution
Incident Ticket Number # INC0285814, *** AK SLA ***, Name - ASOP P3 Issue In Queue , Duration - 3 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - ASOP P3 Issue Resolution , Duration - 4 Days 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
Automation Services Operations
4
1 Day or 23 Hours 59 Minutes
7 Days or 6 Days 23 Hours 59 Minutes
24x7
24x7
ASOP P4/P5 Issue In Queue
ASOP P4/P5 Issue Resolution
Incident Ticket Number # INC0285815, *** AK SLA ***, Name - ASOP P4/P5 Issue In Queue , Duration - 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - ASOP P4/P5 Issue Resolution , Duration - 6 Days 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
Automation Services Operations
5
1 Day or 23 Hours 59 Minutes
7 Days or 6 Days 23 Hours 59 Minutes
24x7
24x7
ASOP P4/P5 Issue In Queue
ASOP P4/P5 Issue Resolution
Incident Ticket Number # INC0285816
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:21:in `And I validate the default ASOP P4/P5 Issue In Queue, 1 Day or 23 Hours 59 Minutes, 24x7 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:9:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_inc2features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:24

Scenario Outline: SLA Testing for Incident - Asignment Group App Support - BRM

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:25
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:26
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:27
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:28
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:29
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:30

Examples

Screenshot
  Screenshot
  Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Incident
App Support - BRM
1
30 Min
1 Hour or 59 Minutes
24x7
24x7
Application Support - BRM P1 INT ACK SLA
Application Support - BRM P1 INT Resolution
Incident Ticket Number # INC0285817, *** AK SLA ***, Name - Application Support - BRM P1 INT ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Application Support - BRM P1 INT Resolution , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
App Support - BRM
2
30 Min
6 Hours or 5 Hours 59 Minutes
24x7
24x7
Application Support - BRM P2 INT ACK SLA
Application Support - BRM P2 INT Resolution
Incident Ticket Number # INC0285818, *** AK SLA ***, Name - Application Support - BRM P2 INT ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Application Support - BRM P2 INT Resolution , Duration - 5 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
App Support - BRM
3
30 Min
12 Hours or 11 Hours 59 Minutess
8x5
8x5
Application Support - BRM P3 INT ACK SLA
Application Support - BRM P3 INT Resolution
Incident Ticket Number # INC0285819, *** AK SLA ***, Name - Application Support - BRM P3 INT ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:36:in `And I validate the default Application Support - BRM P3 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:26:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Incident
App Support - BRM
4
30 Min
1 Day or 23 Hours 59 Minutes
8x5
8x5
Application Support - BRM P4 INT ACK SLA
Application Support - BRM P4 INT Resolution
Incident Ticket Number # INC0285820, *** AK SLA ***, Name - Application Support - BRM P4 INT ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:37:in `And I validate the default Application Support - BRM P4 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:26:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Incident
App Support - BRM
5
30 Min
3 Days or 2 Days 23 Hours 59 Minutes
8x5
8x5
Application Support - BRM P5 INT ACK SLA
Application Support - BRM P5 INT Resolution
Incident Ticket Number # INC0285821, *** AK SLA ***, Name - Application Support - BRM P5 INT ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:38:in `And I validate the default Application Support - BRM P5 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:26:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_inc3features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:41

Scenario Outline: SLA Testing for Incident - Asignment Group App Support - LASER

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:42
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:43
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:44
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:45
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:46
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:47

Examples

Screenshot
  Screenshot
  Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Incident
App Support - LASER
1
30 Min
1 Hour or 59 Minutes
24x7
24x7
App Support - LASER P1 INT ACK SLA
App Support - LASER P1 INT Resolution
Incident Ticket Number # INC0285822, *** AK SLA ***, Name - App Support - LASER P1 INT ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - App Support - LASER P1 INT Resolution , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
App Support - LASER
2
30 Min
6 Hours or 5 Hours 59 Minutes
24x7
24x7
App Support - LASER P2 INT ACK SLA
App Support - LASER P2 INT Resolution
Incident Ticket Number # INC0285823, *** AK SLA ***, Name - App Support - LASER P2 INT ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - App Support - LASER P2 INT Resolution , Duration - 5 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
App Support - LASER
3
30 Min
12 Hours or 11 Hours 59 Minutess
8x5
8x5
App Support - LASER P3 INT ACK SLA
App Support - LASER P3 INT Resolution
Incident Ticket Number # INC0285824, *** AK SLA ***, Name - App Support - LASER P3 INT ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:53:in `And I validate the default App Support - LASER P3 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:43:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Incident
App Support - LASER
4
30 Min
1 Day or 23 Hours 59 Minutes
8x5
8x5
App Support - LASER P4 INT ACK SLA
App Support - LASER P4 INT Resolution
Incident Ticket Number # INC0285825, *** AK SLA ***, Name - App Support - LASER P4 INT ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:54:in `And I validate the default App Support - LASER P4 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:43:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Incident
App Support - LASER
5
30 Min
3 Days or 2 Days 23 Hours 59 Minutes
8x5
8x5
App Support - LASER P5 INT ACK SLA
App Support - LASER P5 INT Resolution
Incident Ticket Number # INC0285826
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:55:in `And I validate the default App Support - LASER P5 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:43:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_inc4features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:58

Scenario Outline: SLA Testing for Incident - Asignment Group UMS DevOps

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:59
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:60
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:61
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:62
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:63
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:64

Examples

Screenshot
  Screenshot
  Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Incident
UMS DevOps
1
30 Min
1 Hour or 59 Minutes
24x7
24x7
UMS DevOps P1 INT ACK SLA
UMS DevOps P1 INT Resolution
Incident Ticket Number # INC0285827, *** AK SLA ***, Name - UMS DevOps P1 INT ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - UMS DevOps P1 INT Resolution , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
UMS DevOps
2
30 Min
6 Hours or 5 Hours 59 Minutes
24x7
24x7
UMS DevOps P2 INT ACK SLA
UMS DevOps P2 INT Resolution
Incident Ticket Number # INC0285828, *** AK SLA ***, Name - UMS DevOps P2 INT ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - UMS DevOps P2 INT Resolution , Duration - 5 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Incident
UMS DevOps
3
30 Min
12 Hours or 11 Hours 59 Minutess
8x5
8x5
UMS DevOps P3 INT ACK SLA
UMS DevOps P3 INT Resolution
Incident Ticket Number # INC0285829, *** AK SLA ***, Name - UMS DevOps P3 INT ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:70:in `And I validate the default UMS DevOps P3 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:60:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Incident
UMS DevOps
4
30 Min
1 Day or 23 Hours 59 Minutes
8x5
8x5
UMS DevOps P4 INT ACK SLA
UMS DevOps P4 INT Resolution
Incident Ticket Number # INC0285830, *** AK SLA ***, Name - UMS DevOps P4 INT ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:71:in `And I validate the default UMS DevOps P4 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:60:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Incident
UMS DevOps
5
30 Min
3 Days or 2 Days 23 Hours 59 Minutes
8x5
8x5
UMS DevOps P5 INT ACK SLA
UMS DevOps P5 INT Resolution
Incident Ticket Number # INC0285831
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:72:in `And I validate the default UMS DevOps P5 INT ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_incident_sla_1.feature:60:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@regression @module1 @sd @brm @sla_validation

Feature: Service Desk SLA Validation

Background

  1. Given I login as a SDTechnician
    features/step_definitions/global_steps.rb:1
@sla_req1features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:8

Scenario Outline: SLA Testing for Request - Asignment Group GET Ops Tier1

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:9
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:10
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:11
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:12
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:13
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:14

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Request
GET Ops Tier1
1
30 Minutes
3 Hour or 2 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P1 REQ ACK SLA
Get Ops Tier 1 P1 REQ Resolution SLA
Incident Ticket Number # INC0285832, *** AK SLA ***, Name - Get Ops Tier 1 P1 REQ ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Get Ops Tier 1 P1 REQ Resolution SLA , Duration - 2 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
GET Ops Tier1
2
1 Hour or 59 Minutes
1 Day or 23 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P2 REQ ACK SLA
Get Ops Tier 1 P2 REQ Resolution SLA
Incident Ticket Number # INC0285833, *** AK SLA ***, Name - Get Ops Tier 1 P2 REQ ACK SLA , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Get Ops Tier 1 P2 REQ Resolution SLA , Duration - 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
GET Ops Tier1
3
8 Hours or 7 Hours 59 Minutes
3 Days or 2 Days 23 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P3 REQ ACK SLA
Get Ops Tier 1 P3 REQ Resolution SLA
Incident Ticket Number # INC0285834, *** AK SLA ***, Name - Get Ops Tier 1 P3 REQ ACK SLA , Duration - 7 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Get Ops Tier 1 P3 REQ Resolution SLA , Duration - 2 Days 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
GET Ops Tier1
4
16 Hours or 15 Hours 59 Minutes
3 Days or 2 Days 23 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P4 REQ ACK SLA
Get Ops Tier 1 P4 REQ Resolution SLA
Incident Ticket Number # INC0285835, *** AK SLA ***, Name - Get Ops Tier 1 P4 REQ ACK SLA , Duration - 15 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Get Ops Tier 1 P4 REQ Resolution SLA , Duration - 2 Days 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
GET Ops Tier1
5
1 Day or 23 Hours 59 Minutes
3 Days or 2 Days 23 Hours 59 Minutes
24x7
24x7
Get Ops Tier 1 P5 REQ ACK SLA
Get Ops Tier 1 P5 REQ Resolution SLA
Incident Ticket Number # INC0285836
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:22:in `And I validate the default Get Ops Tier 1 P5 REQ ACK SLA, 1 Day or 23 Hours 59 Minutes, 24x7 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:10:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_req3features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:26

Scenario Outline: SLA Testing for Request - Asignment Group GSCS DevOps

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:27
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:28
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:29
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:30
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:31
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:32

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Request
GSCS DevOps
1
30 Minutes
3 Hours or 2 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P1 REQ A...
Global Sales & Contract Systems P1 REQ R...
Incident Ticket Number # INC0285837, *** AK SLA ***, Name - Global Sales & Contract Systems P1 REQ A... , Duration - 30 Minutes , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Global Sales & Contract Systems P1 REQ R... , Duration - 3 Hours , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
GSCS DevOps
2
1 Hour or 59 Minutes
1 Day or 23 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P2 REQ A...
Global Sales & Contract Systems P2 REQ R...
Incident Ticket Number # INC0285838, *** AK SLA ***, Name - Global Sales & Contract Systems P2 REQ A... , Duration - 1 Hour , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Global Sales & Contract Systems P2 REQ R... , Duration - 1 Day , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
GSCS DevOps
3
8 Hours or 7 Hours 59 Minutes
3 Days or 2 Days 23 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P3 REQ A...
Global Sales & Contract Systems P3 REQ R...
Incident Ticket Number # INC0285839, *** AK SLA ***, Name - Global Sales & Contract Systems P3 REQ A... , Duration - 8 Hours , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Global Sales & Contract Systems P3 REQ R... , Duration - 3 Days , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
GSCS DevOps
4
16 Hours or 15 Hours 59 Minutes
3 Days or 2 Days 23 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P4 REQ A...
Global Sales & Contract Systems P4 REQ R...
Incident Ticket Number # INC0285840, *** AK SLA ***, Name - Global Sales & Contract Systems P4 REQ A... , Duration - 16 Hours , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Global Sales & Contract Systems P4 REQ R... , Duration - 3 Days , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
GSCS DevOps
5
1 Day or 23 Hours 59 Minutes
3 Days or 2 Days 23 Hours 59 Minutes
8x5
8x5
Global Sales & Contract Systems P5 REQ A...
Global Sales & Contract Systems P5 REQ R...
Incident Ticket Number # INC0285841
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:40:in `And I validate the default Global Sales & Contract Systems P5 REQ A..., 1 Day or 23 Hours 59 Minutes, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:28:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_req2features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:44

Scenario Outline: SLA Testing for Request - Asignment Group Racker Experience

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:45
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:46
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:47
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:48
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:49
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:50

Examples

Screenshot
  Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Request
Racker Experience
1
1 Hour or 59 Minutes
4 Hours or 3 Hours 59 Minutes
8x5
8x5
Racker Experience P1 REQ ACK SLA
Racker Experience P1 REQ Resolution
Incident Ticket Number # INC0285842, *** AK SLA ***, Name - Racker Experience P1 REQ ACK SLA , Duration - 1 Hour , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Racker Experience P1 REQ Resolution , Duration - 4 Hours , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
Racker Experience
2
4 Hours or 3 Hours 59 Minutes
8 Hours or 7 Hours 59 Minutes
8x5
8x5
Racker Experience P2 REQ ACK SLA
Racker Experience P2 REQ Resolution
Incident Ticket Number # INC0285843, *** AK SLA ***, Name - Racker Experience P2 REQ ACK SLA , Duration - 4 Hours , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** 
expected: "Completed"
     got: "In progress"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:395:in `/^I validate the resolution (.*), (.*), (.*) SLA created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:55:in `And I validate the resolution Racker Experience P2 REQ Resolution, 8 Hours or 7 Hours 59 Minutes, 8x5 SLA created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:48:in `And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created'
Request
Racker Experience
3
8 Hours or 7 Hours 59 Minutes
16 Hours or 15 Hours 59 Minutes
8x5
8x5
Racker Experience P3 REQ ACK SLA
Racker Experience P3 REQ Resolution
Incident Ticket Number # INC0285844, *** AK SLA ***, Name - Racker Experience P3 REQ ACK SLA , Duration - 8 Hours , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Racker Experience P3 REQ Resolution , Duration - 16 Hours , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
Racker Experience
4
16 Hours or 15 Hours 59 Minutess
2 Days or 1 Day 23 Hours 59 Minutes
8x5
8x5
Racker Experience P4 REQ ACK SLA
Racker Experience P4 REQ Resolution
Incident Ticket Number # INC0285845, *** AK SLA ***, Name - Racker Experience P4 REQ ACK SLA , Duration - 16 Hours , Schedule - 8x5 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Racker Experience P4 REQ Resolution , Duration - 1 Day , Schedule - 8x5 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
Racker Experience
5
2 Days or 1 Day 23 Hours 59 Minutes
4 Days or 3 Days 23 Hours 59 Minutes
8x5
8x5
Racker Experience P5 REQ ACK SLA
Racker Experience P5 REQ Resolution
Incident Ticket Number # INC0285846
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:58:in `And I validate the default Racker Experience P5 REQ ACK SLA, 2 Days or 1 Day 23 Hours 59 Minutes, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:46:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@billdev1features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:61

Scenario Outline: SLA Testing for Incident - Asignment Group BillingDevOps

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:62
  2. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:63
  3. And validate that only one sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:64

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Request
BillingDevOps
1
N/A
4 Hours or 3 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P1 REQ Resolution
Incident Ticket Number # INC0285847, *** Res SLA validation***, Name - Billing DevOps P1 REQ Resolution , Duration - 3 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress
Request
BillingDevOps
2
N/A
8 Hours or 7 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P2 REQ Resolution
Incident Ticket Number # INC0285848, *** Res SLA validation***, Name - Billing DevOps P2 REQ Resolution , Duration - 7 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress
Request
BillingDevOps
3
N/A
16 Hours or 15 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P3 REQ Resolution
Incident Ticket Number # INC0285849, *** Res SLA validation***, Name - Billing DevOps P3 REQ Resolution , Duration - 15 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress
Request
BillingDevOps
4
N/A
1 Day 8 Hours or 1 Day 7 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P4 REQ Resolution
Incident Ticket Number # INC0285851, *** Res SLA validation***, Name - Billing DevOps P4 REQ Resolution , Duration - 1 Day 7 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress
Request
BillingDevOps
5
N/A
9 Days or 8 Days 23 Hours 59 Minutes
N/A
24x7
N/A
Billing DevOps P5 REQ Resolution
Incident Ticket Number # INC0285852
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:392:in `/^I validate the resolution (.*), (.*), (.*) SLA created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:72:in `And I validate the resolution Billing DevOps P5 REQ Resolution, 9 Days or 8 Days 23 Hours 59 Minutes, 24x7 SLA created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla.feature:63:in `And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created'
@regression @module1 @sd @brm @sla_validation

Feature: Service Desk SLA Validation

Background

  1. Given I login as a SDTechnician
    features/step_definitions/global_steps.rb:1
@sla_req4features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:7

Scenario Outline: SLA Testing for Request - Asignment Group Automation Services Operations

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:8
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:9
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:10
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:11
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:12
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:13

Examples

Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Request
Automation Services Operations
1
1 Hour or 59 Minutes
1 Day or 23 Hours 59 Minutes
24x7
24x7
ASOP P1 Issue In Queue
ASOP P1 Issue Resolution
Incident Ticket Number # INC0285853, *** AK SLA ***, Name - ASOP P1 Issue In Queue , Duration - 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - ASOP P1 Issue Resolution , Duration - 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
Automation Services Operations
2
2 Hours or 1 Hour 59 Minutes
2 Days or 1 Day 23 Hours 59 Minutes
24x7
24x7
ASOP P2 Issue In Queue
ASOP P2 Issue Resolution
Incident Ticket Number # INC0285854, *** AK SLA ***, Name - ASOP P2 Issue In Queue , Duration - 1 Hour 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - ASOP P2 Issue Resolution , Duration - 1 Day 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
Automation Services Operations
3
4 Hours or 3 Hours 59 Minutes
5 Days or 4 Days 23 Hours 59 Minutes
24x7
24x7
ASOP P3 Issue In Queue
ASOP P3 Issue Resolution
Incident Ticket Number # INC0285855, *** AK SLA ***, Name - ASOP P3 Issue In Queue , Duration - 3 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - ASOP P3 Issue Resolution , Duration - 4 Days 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
Automation Services Operations
4
1 Day or 23 Hours 59 Minutes
7 Days or 6 Days 23 Hours 59 Minutes
24x7
24x7
ASOP P4/P5 Issue In Queue
ASOP P4/P5 Issue Resolution
Incident Ticket Number # INC0285856, *** AK SLA ***, Name - ASOP P4/P5 Issue In Queue , Duration - 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - ASOP P4/P5 Issue Resolution , Duration - 6 Days 23 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
Automation Services Operations
5
1 Day or 23 Hours 59 Minutes
7 Days or 6 Days 23 Hours 59 Minutes
24x7
24x7
ASOP P4/P5 Issue In Queue
ASOP P4/P5 Issue Resolution
Incident Ticket Number # INC0285857
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:21:in `And I validate the default ASOP P4/P5 Issue In Queue, 1 Day or 23 Hours 59 Minutes, 24x7 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:9:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_req5features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:24

Scenario Outline: SLA Testing for Request - Asignment Group App Support - BRM

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:25
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:26
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:27
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:28
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:29
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:30

Examples

Screenshot
  Screenshot
  Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Request
App Support - BRM
1
30 Min
4 Hours or 3 Hours 59 Minutes
24x7
24x7
Application Support - BRM P1 REQ ACK SLA
Application Support - BRM P1 REQ Resolution
Incident Ticket Number # INC0285858, *** AK SLA ***, Name - Application Support - BRM P1 REQ ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Application Support - BRM P1 REQ Resolution , Duration - 3 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
App Support - BRM
2
30 Min
8 Hours or 7 Hours 59 Minutes
24x7
24x7
Application Support - BRM P2 REQ ACK SLA
Application Support - BRM P2 REQ Resolution
Incident Ticket Number # INC0285859, *** AK SLA ***, Name - Application Support - BRM P2 REQ ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - Application Support - BRM P2 REQ Resolution , Duration - 7 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
App Support - BRM
3
30 Min
16 Hours or 15 Hours 59 Minutes
8x5
8x5
Application Support - BRM P3 REQ ACK SLA
Application Support - BRM P3 REQ Resolution
Incident Ticket Number # INC0285860, *** AK SLA ***, Name - Application Support - BRM P3 REQ ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:36:in `And I validate the default Application Support - BRM P3 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:26:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Request
App Support - BRM
4
30 Min
1 Day 8 Hours or 1 Day 7 Hours 59 Minutes
8x5
8x5
Application Support - BRM P4 REQ ACK SLA
Application Support - BRM P4 REQ Resolution
Incident Ticket Number # INC0285861, *** AK SLA ***, Name - Application Support - BRM P4 REQ ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:37:in `And I validate the default Application Support - BRM P4 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:26:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Request
App Support - BRM
5
30 Min
9 Days or 8 Days 23 Hours 59 Minutes
8x5
8x5
Application Support - BRM P5 REQ ACK SLA
Application Support - BRM P5 REQ Resolution
Incident Ticket Number # INC0285862
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:38:in `And I validate the default Application Support - BRM P5 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:26:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_req6features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:41

Scenario Outline: SLA Testing for Request - Asignment Group App Support - LASER

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:42
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:43
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:44
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:45
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:46
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:47

Examples

Screenshot
  Screenshot
  Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Request
App Support - LASER
1
30 Min
4 Hours or 3 Hours 59 Minutes
24x7
24x7
App Support - LASER P1 REQ ACK SLA
App Support - LASER P1 REQ Resolution
Incident Ticket Number # INC0285863, *** AK SLA ***, Name - App Support - LASER P1 REQ ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - App Support - LASER P1 REQ Resolution , Duration - 3 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
App Support - LASER
2
30 Min
8 Hours or 7 Hours 59 Minutes
24x7
24x7
App Support - LASER P2 REQ ACK SLA
App Support - LASER P2 REQ Resolution
Incident Ticket Number # INC0285864, *** AK SLA ***, Name - App Support - LASER P2 REQ ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - App Support - LASER P2 REQ Resolution , Duration - 7 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
App Support - LASER
3
30 Min
16 Hours or 15 Hours 59 Minutes
8x5
8x5
App Support - LASER P3 REQ ACK SLA
App Support - LASER P3 REQ Resolution
Incident Ticket Number # INC0285866, *** AK SLA ***, Name - App Support - LASER P3 REQ ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:53:in `And I validate the default App Support - LASER P3 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:43:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Request
App Support - LASER
4
30 Min
1 Day 8 Hours or 1 Day 7 Hours 59 Minutes
8x5
8x5
App Support - LASER P4 REQ ACK SLA
App Support - LASER P4 REQ Resolution
Incident Ticket Number # INC0285867, *** AK SLA ***, Name - App Support - LASER P4 REQ ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:54:in `And I validate the default App Support - LASER P4 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:43:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Request
App Support - LASER
5
30 Min
9 Days or 8 Days 23 Hours 59 Minutes
8x5
8x5
App Support - LASER P5 REQ ACK SLA
App Support - LASER P5 REQ Resolution
Incident Ticket Number # INC0285868
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:55:in `And I validate the default App Support - LASER P5 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:43:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
@sla_req7features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:58

Scenario Outline: SLA Testing for Request - Asignment Group UMS DevOps

  1. And for SLA testing I submit a <ticket_type> with <pri> and <assignment_group>
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:59
  2. And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:60
  3. And when i click on the Work ticket
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:61
  4. And I validate the resolution <res_sla>, <res_duration>, <res_schedule> SLA created
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:62
  5. And I set the request/incident as on_hold, ran, rvn then the stage should be Paused
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:63
  6. And validate that only two sla are displayed
    features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:64

Examples

Screenshot
  Screenshot
  Screenshot
 
ticket_type
assignment_group
pri
ack_duration
res_duration
ack_schedule
res_schedule
ack_sla
res_sla
Request
UMS DevOps
1
30 Min
4 Hours or 3 Hours 59 Minutes
24x7
24x7
UMS DevOps P1 REQ ACK SLA
UMS DevOps P1 REQ Resolution
Incident Ticket Number # INC0285869, *** AK SLA ***, Name - UMS DevOps P1 REQ ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - UMS DevOps P1 REQ Resolution , Duration - 3 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
UMS DevOps
2
30 Min
8 Hours or 7 Hours 59 Minutes
24x7
24x7
UMS DevOps P2 REQ ACK SLA
UMS DevOps P2 REQ Resolution
Incident Ticket Number # INC0285870, *** AK SLA ***, Name - UMS DevOps P2 REQ ACK SLA , Duration - 29 Minutes , Schedule - 24x7 , Stage - In progress , ** Work Ticket Clicked** , AK Stage displayed - Completed as expected, *** Res SLA validation***, Name - UMS DevOps P2 REQ Resolution , Duration - 7 Hours 59 Minutes , Schedule - 24x7 , Stage - In progress , *** Stage valdiation for On Hold, RAN, RVN , on_hold displayed : Paused, ran displayed : Paused, rvn displayed : Paused
Request
UMS DevOps
3
30 Min
16 Hours or 15 Hours 59 Minutess
8x5
8x5
UMS DevOps P3 REQ ACK SLA
UMS DevOps P3 REQ Resolution
Incident Ticket Number # INC0285871, *** AK SLA ***, Name - UMS DevOps P3 REQ ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:70:in `And I validate the default UMS DevOps P3 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:60:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Request
UMS DevOps
4
30 Min
1 Day 8 Hours or 1 Day 7 Hours 59 Minutes
8x5
8x5
UMS DevOps P4 REQ ACK SLA
UMS DevOps P4 REQ Resolution
Incident Ticket Number # INC0285872, *** AK SLA ***, Name - UMS DevOps P4 REQ ACK SLA , Duration - 30 Minutes 
expected: "8x5"
     got: "8x5 exclude holidays"

(compared using eql?)

./features/step_definitions/sd_incident_steps.rb:355:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:71:in `And I validate the default UMS DevOps P4 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:60:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'
Request
UMS DevOps
5
30 Min
9 Days or 8 Days 23 Hours 59 Minutes
8x5
8x5
UMS DevOps P5 REQ ACK SLA
UMS DevOps P5 REQ Resolution
Incident Ticket Number # INC0285873
Element with locator <css='div[id='tabs2_list']>span:nth-child(3)>span>span:nth-child(2)'> not found
./features/step_definitions/sd_incident_steps.rb:350:in `/^I validate the default (.*), (.*), (.*) SLA Acknowledgement created$/'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:72:in `And I validate the default UMS DevOps P5 REQ ACK SLA, 30 Min, 8x5 SLA Acknowledgement created'
features/service_desk_module/service_desk_brm_module/sla_validation/brm_request_sla_1.feature:60:in `And I validate the default <ack_sla>, <ack_duration>, <ack_schedule> SLA Acknowledgement created'